Connect/Binding edges are published into the semantic index alongside
ordinary reference edges, so the impact verb's reference pass followed
every connector a second time: directed instead of undirected, attributed
to the raw nested-port endpoint instead of its owning declaration, and
outside the connector hop bound. Exclude connector edge kinds from
CollectImpactReferences so CollectImpactConnections is their single
attribution path. This bounds connector chains to the hop limit the
summary already claims, and stops one connector producing two entries when
the port sits on the connector's source side.

Replace the impact cycle guard's membership set with a minimum-hop
dictionary and a shared TryReach helper. Connector-hop cost is not
monotonic in breadth-first depth, so an element first reached over a
connector may later be reached over a pure reference path with its hop
budget restored. Re-expand on a strictly cheaper arrival without emitting
a second entry, so nothing within the bound is dropped while each element
keeps its first-arrival depth and relation attribution.

The flag-absent default now reports fewer rows than released versions on
models with declared-endpoint connectors. This is a defect correction, not
a feature removal: the previous behavior contradicted the documented
default and emitted qualified names that cannot be used as query subjects.
It also makes --include-connections a strict superset of the default. The
change is called out in the user guide, README, and design constraints.

Rewrite two mis-named tests onto fixtures that can actually fail, since
every existing connector fixture puts both endpoints on nested ports and
therefore never reaches the defective path. Add fixtures and tests for
both user-reported models and for the hop-minimality case.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Restate SysML2Tools-Core-Query-ImpactHopMinimality as observable behavior
rather than cycle-guard mechanism, and move the guard, minimum-hop record,
and re-expansion detail out of its justification while keeping the
connector-hop non-monotonicity rationale.

Scope the "not resolvable as query subjects" claim to nested-port
endpoints, since declared endpoint names such as Model::System::b do
resolve, and replace the appeal to a "documented default contract" with an
intrinsic characterization of the defect, because that contract text never
shipped in a released user guide.

Reframe the user guide upgrade note, which anachronistically described
prior releases as following connectors "even without --include-connections"
when that flag did not exist, while retaining the warning strength.

Restate the verification acceptance criterion to match the requirement and
lead the hop-minimality traceability row with its public entry point.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Replace the compound Core -ImpactConnections requirement with five atomic
requirements (-ImpactConnections, -ImpactConnectionEndpoints,
-ImpactConnectionRollUp, -ImpactConnectionHopBound, -ImpactConnectionCycles)
and the compound -EntryTraversalMetadata requirement with three
(-EntryTraversalMetadata, -EntryMetadataJsonOmission,
-EntryRelationSerialization), redistributing every test registration. The
"never additionally as a reference edge" and "exactly once" clauses are
dropped rather than re-homed because -Impact and -ImpactHopMinimality
already own them; the exactly-once test moves to -ImpactHopMinimality.

Split the Tool -IncludeConnections requirement into -IncludeConnections and
-IncludeConnectionsHelp, expressed purely as observable CLI behavior with
Core-internal detail removed from both title and justification.

Close the general-help traceability gap with a new Tool test asserting that
'query --help' documents --include-connections.

Correct the Tool design's help-block description, which named a resx key
that does not exist, and correct the user guide's claim that the flag can
never alter an existing row: a connector can re-attribute a row to a lower
depth and a Connect relation.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>